Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1051

reference
550-tree-1
name
1051
tree-preservation-order

undefined

550-tpo-1
uprn
address-text
point
POINT (-1.016920 50.882269)
geometry
MULTIPOLYGON (((-1.016835 50.882260,-1.016839 50.882277,-1.016851 50.882292,-1.016869 50.882304,-1.016893 50.882312,-1.016919 50.882315,-1.016946 50.882312,-1.016970 50.882305,-1.016989 50.882293,-1.017001 50.882278,-1.017006 50.882261,-1.017002 50.882245,-1.016990 50.882229,-1.016971 50.882217,-1.016948 50.882209,-1.016922 50.882207,-1.016895 50.882209,-1.016871 50.882217,-1.016852 50.882228,-1.016840 50.882243,-1.016835 50.882260)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL